Secure digital media capture and analysis

ABSTRACT

Systems and methods for generating certified images, annotations, and incident reports are disclosed. A media capture device can be used to capture a media asset and related metadata. The image and its metadata can then be certified upon capture so that it can be verified as authentic and unaltered after certification. The certified media asset can then be included in or as a part of an incident report, which may optionally align multiple media assets along a path based on location and time of capture. The report may itself be certified and synchronized with a cloud server system.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation and claims the priority benefit ofU.S. patent application Ser. No. 16/505,305 filed Jul. 8, 2019 and setto issue as U.S. Pat. No. 11,212,416, which claims the priority benefitof U.S. Provisional Patent Application No. 62/694,528 filed Jul. 6,2018, the disclosures of which are incorporated herein by reference.

BACKGROUND Field of the Invention

The present invention generally relates to digital media capture andsynchronization. More specifically, the present invention relates tocertification of digital media captured by electronic media capturedevices and generation of reports using the resulting certified media.

Description of the Related Art

User devices such as smartphones or tablets can take photos using camerasoftware applications designed to interact with camera hardware embeddedin the user device. Some of these camera applications store photometadata along with the photo. Examples of metadata include the identitythe user device from which the photo was taken, latitude and longitudeat which the photo was taken, and information concerning use of filtersor other applications that may alter the digital image. The type,format, and details of such metadata are typically inconsistent betweencamera software applications, impossible to verify as unchanged, andincomplete in terms of what data is captured versus what data couldpotentially be captured and tied together. A user of one softwareapplication cannot rely on a specific set of metadata to be presentalong with the same photograph should it be taken in anotherapplication, and the user also traditionally cannot rely on data fromsuch applications being secure or verifiably not tampered with.

Some types of positional, sensor, and other software or hardware data,while available for use, are often not stored as photo metadata or in amanner that allows for pairing of the data with a particular image. Thisdata could be used in the context of other software applications or inthe review of certain photographs. As a result, users may not be able todetermine the exact positioning of a user device, an object beingphotographed, or the output of other sensors while or when the photo wasbeing taken.

Photographs are also often used in creating an incident report. Creatingan incident report usually involves transcribing details of an incidentdetails such as a car accident or structural damage to a home frompersonal or third-party observation to handwritten form. Thosehandwritten notes are then entered into a computer or program operatingthereon. Photographs related to the incident and showing the accident ordamage are usually scanned or uploaded into the aforementioned computeror program by way of a physical or network connection. Traditionally,these images would have be—as a matter of course and necessity—acceptedat face value with no reliable way to ascertain if the images wereauthentic or unaltered. The transcribed information such as the locationand physics of an incident, too, were not always accurate due to humantranscription or data entry error or a misreading of image data.

There is a need in the art to more completely collect available sourcesof metadata as they pertain to digital imagery—both still and moving.Further, there is a need in the art to better correlate such metadata tofiles or documents that may be associated with a digital image. Finally,there is a need in the art to be able to verify the accuracy of adigital image, the metadata therein, as well as any data that might bebased on, related to, or otherwise derived from that image.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an overview of a cloud server storage system thatprovides secure synchronization between a mobile device media capturesystem and a server-based web service accessible through a web portal.

FIG. 2 illustrates secure synchronization using the cloud server storagesystem in the context of digital media concerning an insurance claim.

FIG. 3 illustrates stacked interfaces corresponding to an incident andincident media capture process.

FIG. 4 is a flow diagram illustrating procedures for creating a newincident record and for editing an existing incident record.

FIG. 5A illustrates a user interface for creating or editing a title,category, or comment for an entire incident.

FIG. 5B illustrates a user interface for viewing and searching throughincident details for an entire incident or for any of a set of incidentmedia items corresponding to the incident.

FIG. 5C illustrates a user interface for editing incident details for anentire incident or for any of a set of incident media itemscorresponding to the incident.

FIG. 6 illustrates a topographical map tracking locations, directions,altitudes, and sensor data corresponding to media captured at differentpoints along a route.

FIG. 7 is a table illustrating metadata for three digital media assetscaptured at different times.

FIG. 8 illustrates application of directional and location trackingalongside media capture using sensors on or connected to the mobiledevice and algorithms run on the mobile device and/or on a cloud server.

FIG. 9 illustrates an interface with multiple types of media asset andmetadata analyses, including mapping of media assets and metadata,focused analyses, and elevation analyses.

FIG. 10 illustrates an incident report generated using the analyses ofFIG. 9.

FIG. 11 illustrates an exemplary media capture system and mediacertification system interfacing with different types of user devicesand camera devices.

FIG. 12 illustrates a media capture device with an intelligent animage/video capture system that combines a camera image/video with asensor data set from a sensor system.

FIG. 13 is a flow diagram illustrating an exemplary method for securitycertification and verification of digital media.

FIG. 14 is a flow diagram illustrating generation of a path of a capturedevice aligned to media captured by the capture device.

FIG. 15 is a flow diagram illustrating certification of media,annotations of media, and reports.

FIG. 16 is a block diagram of an exemplary computing device that may beused to implement some aspects of the subject technology.

DETAILED DESCRIPTION

Systems and methods for generating certified images, annotations, andincident reports are disclosed. A media capture device can be used tocapture a media asset and related metadata. The image and its metadatacan then be certified upon capture so that it can be verified asauthentic and unaltered after certification. The certified media assetcan then be included in or as a part of an incident report (e.g., forsocial media, news, or insurance), which may optionally align multiplemedia assets along a path based on location and time of capture. Thereport may itself be certified on a mobile device and synchronized witha cloud server system.

FIG. 1 illustrates an overview of a cloud server storage system thatprovides secure synchronization between a mobile device media capturesystem and a server-based web service accessible through a web portal.

In particular, the architecture illustrated in FIG. 1 illustrates amobile device 105 that represents a media capture device, also referredto as an incident media capture system 110. A touchscreen display (orother display) of the mobile device 105 illustrates a graphical userinterface (GUI) listing different certified media assets—that is,certified images and/or videos and/or audio—of a front of a property.Certified media assets may also include audio and/or various sensorreadings as discussed further. Each listed item in the GUI includes athumbnail of a certified media that can be expanded into the fullcertified media assets, a title describing the certified media assets, agroup (these are all grouped as “front property”), a note, a timestampand date of capture, an icon representing directional and location data,a momentary spinning and numbered icon denoting data is beingtransmitted to the cloud, a checkmark icon representing confirmationthat data arrived and stored in cloud, and a note or description.

The data is captured by the media capture device (mobile device 105) andsensor hardware that connects to the mobile device 105 in a wired orwireless fashion as described further herein. The mobile device 105 andany sensor hardware it is connected to represent the incident mediacapture system 110. The sensor hardware may include manned vehicles orunmanned vehicles that are autonomous, self-driving, remote controlled,and/or semi-autonomous. Such manned or unmanned vehicles include aerial,aquatic, or land vehicles. Sensors on such vehicles may capture data aspart of the incident media capture system 110 as per FIG. 11.

The web portal 125 may be a website hosted at the cloud server system115 or hosted elsewhere on a host server or directly in a data center.The web portal 125 provides access to reports generated by the cloudserver system 115 based on incidents identified via the mobile device105 or the web portal 125. The web portal 125 provides access to mediaassets associated with those incidents and included in those reports.

The cloud server storage system 115 receives the certified media alongwith any other relevant data from the mobile device 105 through theInternet or through a local area network/Intranet. Data relevant to thecertified media may include, for example, a title describing thecertified media, type of media (e.g., “visual, 3D, IR, Time-Lapse, SlowMotion, Square, Panoramic, Lidar”), a group (e.g., “front property”), anote, a timestamp and date of capture, directional and location data,additional sensor data, and a note or description. This information isthen made accessible by the cloud server storage system 115 to a usercomputing device 120 via a web portal 125 through the Internet orthrough a local area network/Intranet.

The user computing device 120 may be any computing device. The usercomputing device 120 may be the mobile device 105 or may be a differentcomputing device.

FIG. 2 illustrates secure synchronization using the cloud server storagesystem in the context of digital media concerning an insurance claim.

Incident and media and data capture system and methods withbi-directional cloud compatible digital output, comprising of mobiledigital devices with lens, shutter, application code and data capablecellular, transceiver or wireless cloud connectivity. The system is afully cloud centralize system, or it can converge platforms to be usedwith a single computer or transceiver equipped digital camera. Thismulti-disciplinary collection and processing system allows for quickrecognition action and processing and vital media and data recordingpreservation/storage of unalterable, irrefutable media, reports anddocuments. The system will process any type of incidents, insurance,flood claims, catastrophe events, accidents, law enforcement events muchmore rapidly than any other system. The system will produce claim lossreports with certified media with media titles, labels, captions, notes,groups all with precision GPS information all integrated into a PDF orother computer format for increased efficiency in performing an adjusteron-site claims loss report. Additional key elements of the systeminclude a fully integrated documentation and dynamic visual GPS enabledtitle, categorized, descriptive media dialog/notes integrated multimediareport generation system incorporating a programmable estimating systemwith preservation features.

Additional features integrated to the system are dynamic sketching toolsto allow users to draw/sketch a property detail with measurement as anadjuster generates an on-site damage reports and adds Incident titles,it's category and voice to text, dynamic forms for data block inputs orkeyboard entered comments along with the incident's media and subsequentmedia details including media title, media group (s), media descriptionis fully integrated into the web dynamic report assembling process andinto the reports when the reports function is activated, and a report isgenerated, saved as an example in PDF format and sent/transmitted viatext, SMS, email or added to an assemblage of a larger report.

This capability includes a media, data, audio transcription and reportprocessing center (photo sheet development system) where media groupsare sorted, rearranged and organized by user controls by groups, bymedia along or with each singular media, its geospatial data and mediatitle/notes/description and groups.

Additionally, the system can utilize digital processing of the media todetermine damages and create loss and replacement estimates which isdata that can be extracted from the media. Measurement of detailsincludes walls, basements, floors, roofs, eves, roof damage by hail,wind or tornado etc.

The system uses secure system log-in by users. As the user receivesclaims to adjust, the adjuster will log into the system using his systemcredentials. The user management i.e. system manager will manage allusers though a password system with permissions of groups of users, orindividual users. The media data, loss data, contents data, adjusterlabor for the onsite loss investigation data is all integrated andprocessed with the continually updated cost estimating portion of thesystem to provide all parties involved in the loss; insured, adjuster,adjuster company, insurance company an insurance estimate along with themedia, loss report, documents, witness statements, prior media takenduring the event, policy information, purchase receipts, ownerverification data, adjuster credentials, advance payment forms,engineering reports and any other document to prove the validity of theclaim including any past damages associated with the claim. All thisdata including the final estimate are preserved into the cloud systemand stored with access provided though the secure, password system, usermanagement, dashboard, third party data access and all associated APIs(Advanced Programming Interfaces).

All claims/incident data is associated with 3D media and GPS precisionlocation, using modern cellular device, cellular antenna systems, RTK,GPS L5 signals to provide precise geographic location, land features,rivers, streams, roads, bridges, buildings, topographic data etc. Thesystem will utilize the gps claims data to integrate into computergenerated maps such as Google Earth, Digital Globe or other sources ofsatellite data. This data is also integrated into the digital devicesystem in real-time if required.

That is that the adjuster can capture media of the property while at thesame time download remote satellite image data from a satellite or other3^(rd) party suppliers to incorporate roof damage, solar panels, i.e.hail, wind, tornado, wildfire, earthquake etc., associated with aparticular event, incident or claim. The precision gps and mediaprocessing of both the satellite data and adjuster collected data canform an extremely precise map of for example hail damage location on aroof and show individual hail damage per shingle while indicating depthof the damage, percentage of damaged area, replacement costs to removedamage and replace to original condition. The system includes a claimconfiguration integrated software process which can configure the claimby type dynamically, i.e. fire, flood, accident, storms, earthquake,hurricane so the adjuster has access to multiple tools necessary toperform measurements, collect media, facts, in which to create loss anddamage estimate reports for distinctly different types of events allusing the same system.

The system also has a dynamic function to create both assigned claimsversus created claims. Assigned claims are where the adjuster would havelimited ability to modify the claim data, media or loss data. TheCreated claim would allow the owner/creator to manage everything aboutthe claim and to manage all aspects of the claim with edit functions toedit the whole claim's data, media, estimate, loss forms, loss data,etc. The system can function as an integrated insurance, insuranceclaims system for providers, insurance adjuster firms or adjusters whereinsurance claims are digitally provided over the network to all partiesfor processing allowing the choice of or not of total transparency tothe insurance company, claims company, adjuster, insured and if requiredthe government if it is a government back NFIP flood claim. The systemprovides domain security, initiation and separation, so data is notcompromised. The claims assigned can be assigned to a particularadjuster and can be assigned automatically in specific groups or in amass intelligent assignment process. The digital device receivesassignments through a preprogrammed or manual synchronization. Menus areprovided to service the adjuster on his digital device for workflow andvisual or audio status indicator of all claims such as new, in process,waiting for follow up, completed, waiting for approval etc. This allowsthe transaction thought the use of fill-in prompts, voice prompts, toneprompts for data and media collected on site of loss or capturing mediaof the insured individual home contents such as furniture or valuableswith labels indicating value, age, and condition with a summing of thevalue.

The real-time GNSS (e.g., GPS) and media capture system plays a role inboth being part of the media and by indicating the current location ofthe adjuster doing the work. The GPS allows anyone having access to thesystem to view the, time, location and travel path of collected media todetermine the real-time adjuster location, time on job, time spent doingthe damage assessment, and time to complete the overall damageinspection and estimate. The system features allow for schedulingadjusters with insured to complete their damage inspection and insuredto communicate, make schedules, appointments electronically, and throughother means, such as internet, mobile app interface, or via text, oremail all with confirmations sent to confirm the time, in route andconfirmation when on-site and ready to begin the property adjustment.Other technologies including certified real-time video, certifiedstreaming video with gps and other attributes called out in thisdocument will also be part of the video whether one way or two-wayreal-time video communication. The system additionally will also acceptthe standard Apple Computer's Facetime or Skype system and anycommercial supplier of video conferencing, or internet meeting systemsuch as Go to Meeting as a usable plug in to make the video or computerconnection for real time customer communications. Certified digitalphotos, video, and audio can be captured/shared/transferred/storedbetween the parties during a real-time video teleconference connectionmeeting.

Further, the digital device with application code, reviews an insuranceclaim assigned to the claims adjuster on the digital device. There arecertain steps required to adjust property for an insurance claim of anykind. The system will perform the actions required with the selectedtype of insurance claim. The digital device is capable of capturing 3Dmedia with centimeter accurate precision gps location and gps media anddata and documenting the property loss/damage and recording that dataand integrating all into a report for insurance claim validation andproof of the loss which validates the carrier to payment.

Claims are maintained in a repository with all communications, claimrecords, documents, media, gps data, communications, initial notice ofloss communication notes, engineering reports, policy data, advancepayments records, property data, prior property loss records, contents,audit records, and required business processes. The system completesmultiple claims assignments and produces the documents for differentinsurance carriers simultaneously using hierarchical domain computersoftware and password controls with a super management user with alldata synchronized between the mobile device and the cloud system. Thesystem allows for hundreds of mobile device users to be connected tovarious different domains simultaneously transmitting, syncing betweenthe digital device and cloud system. The system will accept digitalimages, audio recording, video in multiple resolutions, digital policyinformation, word processor documents, spreadsheets, etc. The system hasmultiple drop-down menus, drop down lists and drop downs, that create asecondary drop-down list as cited in the tracking features shown in thedisplayed layer section. The system also allows the user to selectvarious measurement features, such as conversion from fractions todecimal, form from feet to yards, etc. Measurement can be made usingmedia embedded software solutions to use the media to measure in themedia or process outside of the media. The measurement system can allutilize the digital device's onboard GPS system integrated with themedia system to complete measurement of items in the digital media. Theuser can create 3D reference points in the media and draw lines withfinger or user tools to fix a point in the image and draw lines,circles, squares, reference points, boxes to create measurements, aswell as use integrated tools associated with measurement to calculatethe areas, length, widths, volume, square feet etc., of the damage alongwith their replacement values as the data will be associated with thedamage estimation of the loss whereby the loss damage report informationis integrated and completed, stored, delivered.

There is a method for validating and authenticating the user of theportable device based on the registration and/or profile information ofthe user by the system management administration process and user.

The system's mobile application code (uploaded Incident Media CaptureSystem) allows establishment and incident initiation process. Theincident titles, incident categorizing, insertion of comments, storage,transmission and provides for system synchronization of the mobiledevice to cloud and the cloud web portal and to the mobile devices. Allincidents and incident media and associated data i.e., titles,categories, comments etc., are synchronized end to end with the entiretyof associated data and group incident's media captured, using its userscreen selectable multiple media capture source.

FIG. 3 illustrates stacked interfaces corresponding to an incident andincident media capture process.

The user logs in to the mobile device 105 via interface 305, can createa new incident via “new+” button 310, and can save this incident via“save” button 315.

The user then inputs a title, category, and comments for the incidentvia interface 320. The user can add photographic media via a photobutton 325. The Camera icon button expands to open and expose the camerascreen and operator selectable controls and features. Some of these areselect mode, photo, video, audio. Additionally, photo capture featuresand operational modes such as groups, general, standard, new, reportswhich are user selectable providing media location. Voice operationalcamera trigger is included as an additional mode for fingerless captureoperation/process by using voice activation to capture photo, video, andaudio.

Once the incident is created via the interface of step 320 and the usersaves via save button 325, an incident view interface 330 is opened,showing an incident media list 340 with a number of incident mediaassets (here, four)—showing the media thumbnails, titles, groups, andnotes corresponding to each media asset. These are certified mediaassets, meaning they got through the verification/certification processafter being selected by the user and before being associated with theincident media list 340 of the incident viewed via incident viewinterface 330. The incident view interface 330 also includes a searchbar 335, which can be used to search for a particular incident, group,word, and media asset in the incident media list 340. Alternately oradditionally, the search bar 335 can be used to search for a differentincident.

Users capture media in each incident along with recorded material aboutthat incident with scripted aspects regarding each media. Each mediacontains internally code processed certified media, instantaneously attime of acquisition along with user inserted media titles, media group,media notes/description, and other media attributes, all electronicallyintegrated.

The system maintains a continuous media chain of custody, from theinstant the on-screen camera media trigger or activated selectable voiceactivated capture (system has a separate on-screen camera triggercontrol due to having a separate camera controller) is activated, mediais captured and continues throughout the entire transmission process andfor the total time the certified media and associated data is preservedin the cloud and web portal system.

FIG. 4 is a flow diagram illustrating procedures for creating a newincident record and for editing an existing incident record.

At step 405, the user logs in to the mobile device 105.

At step 410, the user selects “Create New Incident.” New incidentcreation provides a number of possible processes at step 415, includingadding incident title, adding emoji/icons to incident title,selecting/adding incident category, selecting/adding incident comment,searching incidents by title, synchronizing all incidents, addingMM/DD/YYYY date, adding timestamp and time zone (e.g., 11:22:45 PMPacific Time), scrolling incident menu, and viewing application menu(home, synch, etc.).

At step 420, the user adds media to the incident. Adding media providesa number of possible processes, including selecting media type (e.g.,photo, audio, video), selecting camera (e.g., photo, audio, video(including various selectable media resolutions and flash)), selectingsubject then trigger, grouping, camera, trigger est. group, mediatransmission indicator, media audible alert transmission, selectingphoto, selecting media selector, adding media title, caption, legend,annotate media (select tool), validating media, adding notes to media,adding media groups, archiving, searching, group selector, group listview, initiating group media, capturing initial group media, and groupkeyboard/voice to text.

At step 425, additional context can be added to the media, includingincident, media, data management, forms; population of forms andreports; estimation, property data, assigned claims, appointments,location; contact lists, calendar, diary and secure electronicsignatures with date and time along with printed name inserted intocertain forms, title etc.

At step 430, the user selects “Edit Incident.” Incident editing providesa number of possible processes at step 435, including editing theincident title, editing the incident emoji/icons, editing the incidentcategory, editing the comment/note, searching the incident title and tovalidate a media, by user selecting the square with up arrow located intop left of screen when upon selection a validation screen appears toindicate certified or non-certified depending on the selecting andinitiating the validation process, edit, add identifier, synching theedited incidents, and archiving the incident in the web portal.

At step 440, the user edits media for the incident. Editing mediaprovides a number of possible processes, including editing incidentmedia title, editing incident media group, search, selecting “enter anew group,” selecting from group list view, editing text viakeyboard/voice to text, editing media notes, selecting and moving mediafrom one group to another, and archiving the media (e.g., in the webportal).

At step 445, additional functionality is listed, including mobileapplication, tracking system, synchronization, third party datainterface, sketches, drawings, photos, video, audio, and other media.

FIG. 5A illustrates a user interface for creating or editing a title,category, or comment for an entire incident.

The user interface of FIG. 5A is an example of the interface 320 of FIG.3 and of the process operations 415 and 435 of FIG. 4. In particular,the while the interface of FIG. 5A is an “edit incident” interface as instep 435 of FIG. 4, it should be understood that a “create new incident”interface as in step 415 of FIG. 4 may look the same or similar.

In particular, the interface of FIG. 5A includes a title input form 505,which is filled out with a boat icon/emoji as well as the text “May16-26 Alaska Inside Passage.” The interface of FIG. 5A also includes acategory input form 510, which is filled out with the text “Recreation.”The interface of FIG. 5A also includes a comment input form 515, whichis filled out with the text “Grand Princess boarded Pier 27, SanFrancisco, Alaska Inside Passage; San Francisco, Ketchikan, Juneau,Skagway, Mendenhall Glacier, Tracy Arm Fjords, Vancouver, SFO.”

FIG. 5B illustrates a user interface for viewing and searching throughincident details for an entire incident or for any of a set of incidentmedia items corresponding to the incident.

The user interface of FIG. 5B is an example of the interface 330 of FIG.3 and of the process operations 415/425 and 435/440 of FIG. 4. Theinterface of FIG. 5B includes incident details 520, which include theincident title 505, incident category 510, and incident comments 515from FIG. 5A. The incident details 520 also include the search bar 335described in FIG. 3.

The interface of FIG. 5B also includes incident media details 525 foreach listed media asset, including a media title 505, a media group 535(all of the media assets visible in FIG. 5B are in the “SFO Arrival”group), and media descriptions/notes 540.

FIG. 5C illustrates a user interface for editing incident details for anentire incident or for any of a set of incident media itemscorresponding to the incident.

The user interface of FIG. 5C is the user interface of FIG. 5B, but withcertain editing functions activated. That is, one of the media itemsidentifying a media asset and its corresponding incident media details525 (title 530, group 535, description/notes 540) are swiped to the leftvia the touchscreen of the mobile device 105 to reveal four buttons forediting the incident media 440. These four buttons read “edit group” forediting the group 535, “edit notes” for editing the description/notes540, “edit title” for editing the title 530, and “archive” for archivingthe media asset.

An “edit incident” button 435 is also present, which when pressed, takesthe user back to the interface of FIG. 5A, allowing the user to edit theincident details 520.

FIG. 6 illustrates a topographical map tracking locations, directions,altitudes, sensor data, and directional data corresponding to mediacaptured at different points along a route.

In particular, a path 605 is illustrated overlaid over the map 600 ofFIG. 6. The path 605 includes a first location 610 associated with atimestamp reading 12:01:01 PM, a second location 615 associated with atimestamp reading 12:05:16 PM, a third location 620 associated with atimestamp reading 12:09:32 PM, a fourth location 625 associated with atimestamp reading 12:11:56 PM, a fifth location 630 associated with atimestamp reading 12:12:15 PM, and a sixth location 635 associated witha timestamp reading 12:14:27 PM.

The path 605 represents a path of travel of a media capture devicethrough a mountainous region, the media capture device capturing variousmedia assets at each location along the path. In particular, eachlocation includes information overlaid over the map 600 representingmedia captured by the media capture device at that location, inparticular a box with a photographic image captured by the media capturedevice at that location and a strip of video frames of a video capturedby the media capture device at that location or a combination of each. Anumber of icons are also illustrated beside each location, the iconsincluding a compass representing a direction that the media capturedevice is facing (and/or a compass reading of a compass of the mediacapture device), media capture device, an altitude indicator indicatingaltitude or elevation as captured by an altimeter of the media capturedevice, a location indicator indicating GNSS geolocation or othergeolocation data captured via one or more positioning receivers off themedia capture device, a metadata icon representing image and videometadata captured by the media capture device, a timer icon representinga time of capture and/or a duration of capture (e.g., for a video), alens icon indicating media capture settings (e.g., aperture, ISO,exposure time, gain), a certification icon indicating certification ofthe media and other data collected by the media capture device asdiscussed with respect to FIG. 13, a cloud icon reflectingsynchronization with servers 115 and/or other user computing devices 120as discussed with respect to FIG. 1 and FIG. 2, a map icon reflectingmap data that can optionally be pulled from internet-accessible mapinformation databases or other sources and optionally includingsatellite or aerial or street-view photography from such sources, and antri-arrow and angle icon representing pitch and roll and yaw captured bythe media capture device.

The media capture system will maintain collected media and associatedmedia data information if operated off grid in a non-cellular signal orWI FI service area. Once signal is detected, the media capture systemwill automatically (or by manual process) upload media and associatedinformation to the cloud. If any data issues are indicated, the uploadsignal is shown. The user, at any time, can complete a systemsynchronization, and all data will be synchronized across both the cloudand on the digital device within or outside a domain structure. Thisincludes the (a.) INCIDENT title, category, comments/notes. This alsoincludes the (b.) MEDIA title, group, group title description, location,time, date, heading, altitude, GPS, certification, cloud confirmation,metadata, device type, device model, device user. The media capturesystem will track information regarding each media showing the startinitiation media time, location, look angle, orientation, compassheading, stop time, movement time to next media capture, next mediacapture, acceleration, velocity/acceleration, time from last capture tothe latest capture, and continuing data tracking until final capture iscompleted. Further, it will generate a map of the data collected andstoring both the data and map in the system. All of this data istransmitted to the cloud and synchronized as well during the collectionprocess. Using RTK signals from suppliers of those type of signals andothers who generated corrections to standard GPS signals, the mediacapture system will also include the ability to utilize miniature GPSreceivers and produce a precise centimeter accuracy incorporated intothe media metadata of anywhere on the earth, underwater or in space.This media accuracy collection and transmitted within the system to thecloud for more precise media tracking and media précises elevationreporting. The map 600 of FIG. 6 is an example of a topography map witha path 605 having a starting point 610. A media capture device is shownat point 610 at a time, location, pointing angle of the lens, elevation,compass heading, 3-axis orientation of the lens, capturing a media. Thesystem then moves to point 615. From point 610 to point 615, the time,velocity, elevation, acceleration, compass heading, lens's look angle,map location, metadata, media certification, are all processed todetermine the outcome and transmitted to the cloud. The system thencontinues on to 620, 625, 630, and on to 635, which is the end of thepath 605. The system which can be integrated directly as a stand-alonedigital device or into a standard digital camera, 3D camera or, any typeof autonomous vehicle camera system, auto/truck dashcam, police bodycamera, aircraft portable or fixed camera system, UAV camera, UAVdashcam, helicopter, boat, attached to delivery driver such as Amazon,FedEx, United Parcel Post, US Post office, or Uber, Lyft dash camerasystems motorcycle or drone.

FIG. 7 is a table illustrating metadata for three digital media assetscaptured at different times.

In particular, FIG. 7 is an example metadata that can be captured by themedia capture device alongside capture of media assets, for examplealong a path such as the path 605 of FIG. 6. The metadata may includetimestamp and location data associated with each media asset (i.e., eachimage, video, and/or audio recording captured by the media capturedevice) as illustrated in FIG. 6. The metadata for each location,timestamp, and media asset may also include additional information, suchas the information identified in the table 700 of FIG. 7, includingMedia identifier (ID) 705 of the media asset, media asset Title 710,Group 715 that the media asset is in (and optionally title of thegroup), Location 725 (optionally including elevation), orientation 730(including roll, pitch, and/or yaw), direction (of movement or ofcapture) and optionally acceleration in the direction (or in any otherdirection) 735, distance and/or time and/or elevation and/or directionsince last capture 740, user identifier (ID) 745, device model and type750, angle that the media capture device is facing 755 (in degrees froma defined direction such as north or east or west or south) duringcapture of the media asset, media type 760 (e.g., image, 3D, video,audio, RADAR, LIDAR, SONAR/SODAR), a distance and/or bearing to a targetobject that is depicted in the media asset 765, order of location withinthe set of locations in the path 770, and additional mapping data 775such as digital elevation model mapping. Additional metadata may alsoinclude Direction Traveled and Dwell time at a particular point. Themetadata illustrated in the table 700 that relates to motion, direction,and orientation may be determined coupling one or more inertialmeasurement units (IMUs), one or more accelerometers, one or moregyroscopes, one or more positioning receivers (GNSS and/or otherwise),or some combination thereof. Metadata may then be incorporated intocharts or graphs, reports and may be overlaid over maps such as the map600 of FIG. 6.

FIG. 8 illustrates application of directional and location trackingalongside media capture using sensors on or connected to the mobiledevice and algorithms run on the mobile device and/or on a cloud server.

In particular, FIG. 8 is an example of path 800 of a media capturedevice from a start point 802 to an end point 828, with media capturedat various times and locations along that path. The media capture devicecaptures a media asset at location 802 at 65 degrees at 9:25:10 AM (thestart point), then moves to location 804 and captures media at 60degrees 9:25:14 AM, then captures a media asset at location 806 at 330degrees at 9:25:16 AM, with these three captures (802, 804, 806) beingin a first group 830. The media capture device then captures a mediaasset at location 808 at 280 degrees at 9:25:23 AM, then moves tolocation 810 and captures media at 330 degrees at 9:25:33 AM, thencaptures a media asset at location 812 at 240 degrees at 9:25:45 AM,with these three captures (808, 810, 812) being in a second group 832.The media capture device then captures a media asset at location 814 at165 degrees at 9:26:10 AM, then moves to location 816 and captures mediaat 150 degrees at 9:26:20 AM, then captures a media asset at location816 at 135 degrees at 9:26:30 AM, then captures a media asset atlocation 818 at 120 degrees at 9:26:40 AM, with these four captures(814, 816, 816, 818) being in a third group 834. The media capturedevice then captures a media asset at location 820 at 80 degrees at9:27:12 AM, then moves to location 822 and captures media at 90 degreesat 9:27:30 AM, then captures a media asset at location 824 at 90 degreesat 9:28:09 AM, with these three captures (820, 822, 824) being in afourth group 836. The media capture device then captures a media assetat location 826 at 225 degrees at 9:28:52 AM, then moves to location 828and captures a final media asset of the path 800 at 185 degrees at9:29:03 AM, with these two captures (826, 828) being in a fifth group838. The path 800 is illustrated from a top-down view, with thelocations plotted along latitude and longitude, with a compass 860showing relative direction within the path 800. Direction of the mediacapture device during capture of each media asset (e.g., image, video,audio) is also captured and shown along the path 800 via the arrow andfield of view indicator extending from the circle.

Images representing the media captured at each location and timestampillustrated along the path 800 (and described above) are shown incallout boxes extending from each location along the path 800. Inparticular, the locations illustrated in the first group 830 and secondgroup 832 represent locations outside of a building, and thecorresponding images are illustrated showing the exterior of thebuilding from different angles representing the view of the buildingfrom those locations. The locations illustrated in the third group 834,the fourth group 836, and the fifth group 838 represent locations insideof the building, and the corresponding images are illustrated showingvarious portions and angles within the interior of the building, withthe images of the third group 834 showing a first room (an entranceroom), the images of the fourth group 836 showing a second room (abedroom), and the images of the fifth group 838 showing a third room (abathroom).

In some cases, additional data may be collected by the media capturedevice, such as location, elevation, altitude, velocity, speed, roll,pitch, and yaw. Velocity or speed may alternately be calculated, forexample based on the various locations and associated timestamps alongthe path 800. Distances between the different locations of the path 800may be determined after or during movement of the media capture devicealong the path 800. In some uses, a predetermined location may beestablished. For example, collecting 3D certified images allows those tobe directly inserted into CAD program to produce a 3D model of thehouse.

Ultimately, all of the media asset data, and related metadata concerninglocation of the media capture device during capture, timestampcorresponding to time of capture, direction that the media capturedevice is facing during capture, is then transmitted to the cloud asdiscussed with respect to FIG. 1 and FIG. 2, and analyses can begenerated. The analysis may include a path such as the path 800 shown inFIG. 8, which may be generated after the media assets and metadata areall captured to align media assets and directional data to the path atthe various locations, which are arranged into the path 800 based on thetimestamps corresponding to the locations. In some cases, altitude orelevation data (or any other metadata as discussed with respect to thetable 700) may be aligned to the path beside a particular location andmedia asset to which that particular data pertains. In some cases,metadata may be represented using colors along a color spectrum coloringa dot/circle/point/shape/icon representing a particular location. Forexample, if the metadata represented by color is altitude, red mayrepresent sea level (or another lowest level of altitude in a range),orange may represent a higher altitude, yellow may represent a stillhigher altitude, green may represent a still higher altitude, turquoisemay represent a still higher altitude, blue may represent a still higheraltitude, indigo may represent a still higher altitude, and violet mayrepresent a highest altitude in a range. The analysis may also includeanalyses such as the analyses 900 illustrated in FIG. 9 and included inthe report of FIG. 10. Certified media captured from the media capturedevice, which may be a 3D camera, from known locations/positions can beinserted into CAD software to generate 3D view of damage to roofs,exteriors, interiors, etc., and converted into insurance reports todocument damage along with mapping location of inspector travelingaround a property.

FIG. 9 illustrates an interface with multiple types of media asset andmetadata analyses, including mapping of media assets and metadata,focused analyses, and elevation analyses.

In particular, FIG. 9 provides an interface 900 with three analyses—amap interface 910 that plots multiple media assets and correspondingmetadata on a satellite view map, a focused analysis 920 that focuses ona particular media asset and related metadata, and an elevation analysis930 that plots elevation. The map 910 shows multiple certified mediaassets at captured different locations that are close to one another,with a particular media asset 915 highlighted with a callout box. Themedia asset 915 is a photo captured on 7/12/2016 at 11:02:16 AM atlatitude 37.65127716 and longitude −121.85468246, with a media asset IDof MDI2016467029. An address in the corner of the map 910 identifiesthat the map 910 is centered around 341 Dove Drive, 94566 USA.

A focused analysis 920 focuses on a particular location or area with anaddress of 341 Dove Drive, 94566 USA that is a target of one or moremedia assets captured around a particular location and time. Metadata ispresented in the focus analysis 920, including a job number (416812)associated with capture of the media assets, a GNSS point associatedwith a center of the property (GPS address property center point), anidentifier of a closest fiduciary survey marker (Bingo 38), anidentifier of a nearest cellular tower (87654 at bearing 330 degrees), anearest cross street (Dove Drive and Grant Court), and a nearest Wi-Fisource (network Xfinity 663). A mini-map is also illustrated showing therelative positions of a cellular antenna 1.812 miles away at 286degrees, a fiduciary survey point 1.765 miles away at 330 degrees, anearby fault line that is 2.3 miles away at 120 degrees, and a nearbyriver water hazard that is 2.8 miles away at 245 degrees.

The elevation analysis 930 illustrates elevations at which various mediaassets were captured relative to a base elevation of 620 feet. The mediaassets are arranged from left to right in the order they were captured.The media assets include a first media asset 942 captured at elevation619 feet and 0.5 inches with the media capture device facing an angle of65 degrees, a second media asset 944 captured 360 degrees away from thefirst media asset 942 at elevation 616 feet with the media capturedevice facing an angle of 60 degrees, a third media asset 946 captured10 degrees away from the second media asset 944 at elevation 619 feetwith the media capture device facing an angle of 120 degrees, a fourthmedia asset 948 captured 50 degrees away from the third media asset 946at elevation 618 feet with the media capture device facing an angle of165 degrees, a fifth media asset 950 captured 88 degrees away from thefourth media asset 948 at elevation 618 feet and 30 inches with themedia capture device facing an angle of 120 degrees, a sixth media asset952 captured 91 degrees away from the fifth media asset 950 at elevation618 feet and 10 inches with the media capture device facing an angle of210 degrees, a seventh media asset 954 captured 115 degrees away fromthe sixth media asset 952 at elevation 619 feet with the media capturedevice facing an angle of 240 degrees, and a final eighth media asset956 captured 180 degrees away from the seventh media asset 954 atelevation 618 feet and 10 inches with the media capture device facing anangle of 0 degrees. The GPS property center lies along the path betweenthe fourth media asset 948 and the fifth media asset 950. The distancecovered between each location corresponding to each media asset isdenoted with a rightward arrow regardless of direction along alatitude-longitude plane (or globe), with direction along alatitude-longitude plane (or globe) denoted instead by the angle writtenabove the arrow. The relative distances between the locations may bedenoted by the relative lengths of these arrows, so that longer arrowsdenote further distances between locations while shorter arrows denoteshorter distances between locations. Alternately, the relative timesbetween capture of each media asset may be denoted by the relativelengths of these arrows, so that longer arrows denote more time elapsedbetween capture of two media assets while shorter arrows denote lesstime elapsed between capture of two media assets. In some cases, thedistances and/or timestamps may be included in the elevation analysis930.

FIG. 10 illustrates an incident report generated using the analyses ofFIG. 9.

The incident report 1000 includes the map analysis 910, focus analysis920, and elevation analysis 930 of FIG. 9 as well as a media mappingpath 1010, a metadata table 700, an incident description 1020, a secondarea map 1030, and a street view image 1040. The incident description1020 may include, for example, incident titles, categories,descriptions, and a date and times of the incident and/or of when thereport was automatically generated by the cloud server system. Theincident description 1020 also identifies multiple media asset relevantto the incident and corresponding incident media titles, groups, datesof capture, timestamps of capture, authors, locations, certificationstatuses, media identifiers, electronic signatures and notes.

Reports may be automatically generated to include media sheets—that is,grids, lists, or other arrangements of media assets and related data.Where the media is entirely photos, these may be photo sheets. Where themedia is entirely videos, these may be video sheets, for example withmultiple frames of the video displayed.

Provided in this new capability is the ability to provide thattechnology and with the associated software to create accurate groundtruth waypoints with accuracy and details never before accomplished inreal time. The application exploits dead reckoning algorithms to producea position 1 location vs a position 2 in 6-axis real time measurementincluding dwell times.

Machine and user insertion into the metadata regarding the concurrentcaptured media details and facts about each media are also processed inthe digital media capture device and autoloaded at the time of capture.The media information data is editable upon capture and later editableby numerous mean of media attributes via voice or keyboard; such asIncident Title, Incident Category, Comments about an Incident. Uponsaving the Incident and using the media capture system for capturingimages, video or audio into the system, and saving the Incident, theIncident detail page which already contains the previously insertedIncident title, category and comments appears and shows a Group searchbar along with the media thumbnails of the Incident captured media. Ifthe group system is utilized, each media is shown in its individualidentified group, and can be searched by using the group searchfunction. Each thumbnail contains the individual media Search, Title,Group Identifier, and Media Notes along with other icons showing cloudreceipt, time date, time zone, and selectable map tool when selectedbring up a map of the media asset capture location and other metadatainformation. Media can also be transferred from group to group using the“edit group” feature. Notes may be edited by using the “edit notes”feature. Titles can be edited by using “edit title” feature.

The identical information is synchronized between the mobile device andthe cloud website and vice versa. It is available to the user afterlogging into the secure website. A similar set of tools are available inthe web portal to identify each incident and each media associated witheach incident. Here is a list of some of those attributes. Each Incidentincludes a unique Incident ID number (generated by the mobileapplication code), Incident number (generated by the mobile applicationcode), Title, Domain, Category, Location, Description, Media,Certification, Authentication, Validity, icon with metadata indicatingCertification, Authentication and Validity, Media icons for photo,video, audio, Assigned Group, assigned to, Priority, Status, Media Qty,Reports, Create On, Create By, Archived, Action; Edit incident, OpenQuick view, Open Storyboard, GPS location, time, date, Plot Geo Tags,Mapping Tools, Report Development System, Search, Archive Incident,icons for mapping media, storyboard access, other actions, such as edit,dashboard, participants; personnel, subjects, contacts, management,configuration, members, audit, system reports, remote mobile applicationsettings for download, revisions, controlling features, mediaresolution, accesses, default settings as example, setting selectablecategories on mobile device and security parameters for thecertification system.

Interface screens on the digital device provide user informationintegrated with work product and reports includes to name a few aremapping, GPS, Media along with, interactive control features (pop-upmenus or slide up menus, or slide across, or grey areas) to highlighteditable text for visual effects for both the camera system andinformation display menus. Additionally, an insurance claim documentingprocess can be performed using the initial claim information, includingthe claim number, the insurance policy number, the adjuster firmprocedure process, assignment of claims, the processing of the claim byan adjuster utilizing a digital device and creating the lossinformation. This can be done by a menu structure, or fill in theblanks, or by audio prompting using a user selection, insertinginformation, tone or a voice. Every item will be collected or driven bythe mobile computer application and immediately transmitted to the cloudand received on the other side of the cloud. This data can then be usedto write formal reports, estimates, drawings, sketches and complete anInsurance claim or allow the ability to complete a virtual desk adjustthe claim by using the certified media, the loss report generated by themobile device with the media, adjuster credentials, and other formsrequired to satisfy the insurance carrier's requirements to pay funds tothe insurance for their loss. Various screens also include metadatalayers. Image layer with the ability to touch the screen and a map isvisualized. This also will allow a voice note on each image when theimage is touched. The voice will describe the title, notes, group andmedia description just by touching the image located either on themobile device or on the cloud connected computer. Each image has theability to play the image number, title, group, claim number, insurer,policy number, notes, description, location and has a volume control andsend image to other feature.

Machine and user insertion into the metadata regarding the concurrentcaptured media details and facts about each media are also processed inthe digital device and autoloaded at the time of capture. The mediainformation data is editable upon capture and later editable by numerousmeans of media attributes via voice or keyboard; such as Incident Title,Incident Category, Comments about an Incident. Upon saving the Incidentand using the media capture system for capturing images, video or audiointo the system, and saving the Incident, the Incident detail page whichalready contains the previously inserted Incident title, category andcomments appears and shows a Group search bar along with the mediathumbnails of the Incident captured media. If the group system isutilized, each media is shown in its individual identified group, andcan be searched by using the group search function. Each thumbnailcontains the individual media Search, Title, Group Identifier, and MediaNotes along with other icons showing cloud receipt, time date, timezone, and selectable map tool when selected brings up a map and maps itsmedia location. Media can also be transferred from group to group usingthe “edit group” feature. Notes may be edited by using the “edit notes”feature. Titles can be edited by using “edit title” feature.

The identical information is synchronized between the mobile device andthe cloud website. It is available to the user after logging into thesecure website. A similar set of tools are available in the web portalto identify each incident and each media associated with each incident.Here is a list of some of those attributes. Each Incident includes aunique Incident identifier (ID) number (generated by the mobileapplication code), Incident number (generated by the mobile applicationcode), Cloud website Authentication, Verification, Certification Systemverifies each media and marks accordingly, Title, Domain, Category,Location, Description, Assigned Group, assigned to, Priority, Status,Media Qty, Media Type, Reports, Create On, Create By, Archived, Action;Edit incident, Open Quick view, Open Storyboard, Plot Geo Tags, ArchiveIncident

Interface screens on the digital device provide user informationintegrated with work product and reports includes to name a few aremapping, GPS, Media along with, interactive control features (pop-upmenus or slide up menus, or slide across, or grey areas) to highlighteditable text for visual effects for both the camera system andinformation display menus. Additionally, an insurance claim documentingprocess can be performed using the initial claim information, includingthe claim number, the insurance policy number, the adjuster firmprocedure process, assignment of claims, the processing of the claim byan adjuster utilizing a digital device and creating the lossinformation. This can be done by a menu structure, or fill in theblanks, or by audio prompting using a tone or a voice. Every item willbe collected or driven by the mobile computer application andimmediately transmitted to the cloud and received on the other side ofthe cloud. This data can then be used to write formal reports,estimates, drawings, sketches and complete an Insurance claim, a virtualclaim or allow the ability to desk adjust the claim by using thecertified media, the loss report generated by the mobile device with themedia, adjuster credentials, and other forms required to satisfy theinsurance carrier's requirements to pay funds to the insurance for theirloss. Various screens also include metadata layers. Image layer with theability to touch the screen and a map is visualized. This also willallow a voice note on each image when the image is touched. The voicewill describe the title, notes, group and media description just bytouching the image located either on the mobile device or on the cloudconnected computer. Each image has the ability to play the title, group,notes, description and has a volume control and send image to otherfeature.

Additional details such as the situational awareness, all displayed onvarious types of base maps, satellite photos, or computer generatednational, state, city, county, towns the quantity of incidents, quantityof media per event, quantity groups of media per group, quantity ofmedia in groups all are appended with date, various icons representingtime, GPS, media location, orientation, heading, elevation, magneticnorth indication, media watermarks, a digital control unit in cameraprovides certification/validation, editable individual media titles,categories, notes, map, cloud receipt marker, in process statusindicator, audible/visual transmission verification mark sharing samethru bi-direction-communication and synchronization with the cloudportion of the system with the role of system management, mobileapplication management, electronic digital media organization, control,preservation, processing, storage and dissemination.

The system is made up with two major elements tied together withsoftware and bi-directional communication. The parts are: a securemobile application uploaded on a digital device capable of mediacollection and transmission. The second element is a secure web andcloud ecosystem that bi-directionally communicates with the mobiledigital system and preserves, processes, stores, reports, and providessecure access to users to The system is made of an unlimited number ofmobile devices, users and cloud real-time communicative secure datainteractive system that captures, collects, certifies mediasimultaneously using a secure mobile application on a digital devicewhile organizing and using the information from the collection processand details contained within the media; such as who, where, why, how,and other metadata; location, orientation, time/date, elevation, cameraheading, acceleration, metadata, velocities, encryption along with otherintegrated data forms such as; editable titled events and incidents withdiffering editable groups of group identified media either captured nowor in the future additive to prior established groups with category,title, captions, descriptions, notes, media title, metadata integratedwithin the individual media provides data that is used in the processorganizing and maintained and storing data in a media information systemso that it can be instantly interacted with at a moment's notice eitheron a desktop or remoted digital device. The media information systemprovides the framework to keep track and organize of the collection,processing, storage, dissemination, viewing, reporting, transmission,interaction, interrogation auditing, tracking of the media data.

One example is the process a media goes though in its digital life. Ahuman using a computer, software and computer process may add, change,modify, edit or remove a voice to text, voice to text title, note,description, caption, to or from a media. Additionally, the media may bealtered or modified, for example using photo editing software and/orvideo editing software and/or audio editing software. The mediaInformation system must keep track of each of the permutations andrevisions that the media has undergone during the its digital life whileresiding in the media information system. The media information systemcreates a permanent record stored at capture or later as modified by thesystem in the cloud with all of the associated data. The system has anintegral audit function that shows a detailed record to the user eachtime the media has been moved, changed, organized, edited, printed, orchanged in any way. This audit feature is the artificial intelligentsystem process allowing learning, digital reading of words, notes,caption associated with the media which provides outputs of the systemin a form upon human request.

Each media capture has a group, category, title, note, caption,description, metadata, GPS, compass heading, relationship tomagnetic/true north, elevation, orientation, certification, validation,image identification number/code, time and date attributes which allowusers to now understand information contained in the media itself. Somephotos/videos have at a date printed on the image itself from the photoprocessor or film stock. Other information surrounding the photodetails/information itself is lost or forgotten over time. The MediaInformation System overcome the past by incorporating all the details ofthe media over its life and continues to expand the details as ittravels through its digital life. As the conversion from analog todigital media is complete, little has been done to organize other thanalbums, face view, search on Apple or Microsoft Web platforms. Thesesystems are complex and hard to use and are not a system. By that, theyupload media from many sources. This media system described herespecifically loads images from only the mobile application. Thatmaintains the process. The system will allow media to be uploadedhowever those media will not be certified and the originality of thedata cannot be proven nor trusted. There is a need for a system thatincorporates the collection, processing and storage of media whichincorporates the totality of data associated with the media at captureso as to not lose the information contained in the image itself by nottaking the steps to preserve it and nurture its digital life.

The system provides benefits and improvements to efficiency (throughautomated generation of paths and mapping interfaces) and speed totechnologies used in many industries. It can be used for qualityassurance, litigation media evidence and preservation, lifesaving suchas being able to locate a user from last media captured on their digitaldevice before going missing or following the media trail as thisapplication teaches. A lot of recent lost or missing humans take a mediain the area they go missing from and this invention provides a new toolfor first responders and police to timely locate a missing or losthuman, law enforcement certified media evidence collection, fire marshalarson investigations, and preservation, transportation i.e. documentingairline issues from globally remote locations such as parts failurewhere the system allows collaboration in real-time with media of theissues available on attendee's computer or mobile device with 100%availability. A new recreational photo system integrating drone media,Aerial trips can be documented, along with weather observation andaerial phenomena. Medical community in that hospitals can documentprocedures, accidents, gunshots, claimed conditions including x-rays andwitness audio recordings at the time of the incident with certifiedmedia possibly lowering medical insurance policy fees. The hospitalityindustry can create historical documented recorded of the status,quality, maintenance issues, theft, fraud, guest damage, water damage,accident, incidents by capturing media which will remain in the systemwith title, notes, descriptions, location, orientation, heading,elevation, metadata providing detailed information of the digital devicecapturing the media, model number, version number, among some of themany attributes.

The system operation can begin on either the website or the mobileapplication which can be downloaded from the website or third party suchas an Application Store or marketplace. The website has a built-inconfiguration control and understands the version history of everymobile application tethered to the system. After login, a number ofinterfaces will appear. Stepping through various interfaces of thesoftware application that runs on the media capture device provides theactions, functions, transmissions, search, media review and otheractivities discussed herein.

Upon the application download, a user can insert username and passwordthat was provided previously upon system registration to sign into asystem. Another interface may appear listing a number of incidentscontained in the system by or otherwise accessible to the logged inuser. In one example, the user may have a total of 792 incident recordsin the cloud system 115. The user may select, for example, the 4thincident down on the incident list page. This is an incident that hasbeen previously captured and stored in the system. Using the systeminformation, the user can see the information about the incident such asan example below:

INCIDENT Title May 16-26 Alaska Inside Passage (269) Media Media Group:SFO Arrival (note time/date/zone/lat/long/Heading/Elevation Media Notes:“Under the Golden Gate Bridge” Added to the incident is an emoji of aboat for quick visual reference.

The user may request generation of a new incident, and can add a title,category/group, and notes/description to the new incident. A media assetmay be captured then, or may be selected from previously captured mediaassets. The media asset is certified as discussed with respect to FIG.13. Additional textual, graphical, or voice-based notes or annotationsmay be added to the media asset and/or to the incident report. Theincident report is then created based on the media asset, optionally itsannotations, the incident notes or descriptions input by the user. Theincident report is then transmitted to the cloud server storage system115.

FIG. 11 illustrates an exemplary media capture system and mediacertification system interfacing with different types of user devicesand camera devices.

The image capture device collects an image as well as sensor data (asseen on the left side of FIG. 11). The data is then autonomously sent tothe internet/cloud system where the digital data is filed, stored andaccessed through the web in a systematic or serialized format constantwith image identification formed with the image capture device (as seenon the right side of FIG. 11). This data can be transferred over a wiredor a wireless connection. In some embodiments, the image capture devicecan first synchronize its image and/or sensor data with a second device.For example, a camera device (e.g., a digital point-and-shoot camera)may first be required to synchronize its data with a user device such asa smartphone or wearable device, which can then form a connection to theinternet/cloud system. In the future these devices, i.e. handhelddigital cameras, body cameras, binoculars can contain the certifiedmedia capture and transmission system and interact directly with thecloud as well as the second device.

The internet/cloud system can include one or more server systems, whichmay be connected to each other. In one embodiment, this internet/cloudsystem is a wireless multiplexed system for securely storing digitaldata to and from mobile digital devices. In another embodiment, thedigital data (e.g., images, reports) are securely held in one centralplace, either by a hardware memory device, server, or a data center.

Once the data is in the internet/cloud system, it may be accessiblethrough a web portal. This web portal may include image-editing tools,worldwide access, and collaboration mechanisms available to its users.Security, digital signature, electronic signatures, watermarking,encryption physical access, password credentials area can be utilizedthroughout the system. Original digital data can be confirmed, saved andprotected though various technologies and system controls. The data canbe further sent to other data systems such as one or more distributedledgers (e.g., one or more blockchain ledgers) for other downstreamuses. The certified data remains unchanged and in its original conditionwithin the distributed ledger, and mechanisms within the distributedledger may further ensure that anyone with access to the distributedledger can verify authenticity. For example, each block of a blockchaindistributed ledger may include a hash of the previous block, or a hashof the previous header, which, can be verified by a viewer re-computingthe hash for any particular block and checking it against the hashstored in the next block. In some cases, blocks of a blockchain can alsoinclude a Merkle Root that represents a hash of hashes of

the entire ledger up until (and optionally cases including) the block inquestion, which can be verified in a similar way. In some embodiments,certain data integrity precautions can be taken as discussed withrespect to FIG. 13.

FIG. 12 illustrates a media capture device with an intelligentimage/video capture system that combines a camera image/video withsensor data set from a sensor system.

A camera image is captured by the media capture device 1200 using acamera embedded as a part of an media capture device 1200. The mediacapture device 1200 can be, or can include, a camera such as a digitalor analog point-and-shoot camera, a digital or analog single-lens reflex“SLR” camera, a digital or analog image-capturing telescope, a digitalor analog image-capturing microscope, binoculars, UAV, drone,surveillance, alarm system, doorbell camera system or a digital oranalog camcorder. Consumer electronic devices with imaging componentrymay also be used. For example, the media capture device 1200 can be aportable consumer user device such as a smartphone, a tablet device, alaptop computer, a wearable device, a portable gaming console, set topdevice, body camera, dashcam, appliance camera, gaming system, or aportable media player device all incorporating a wireless communicationtransceiver interface. Less mobile devices may also be used such asdesktop computers, television systems, gaming consoles, and varioustypes of conveyances.

The intelligent image sensor of the media capture device 1200 allows theuser to capture images and video with greater precision and, further, tocollect and gain access to metadata about the images or video. Themetadata can include, for example, the exact location in latitude,longitude, and elevation of the image capture device. Capturedinformation may further or alternatively include the roll of the imagecapture device, the pitch of the image capture device, the yaw of theimage capture device, the velocity and/or direction of the image capturedevice, the viewing angle of the image capture device, the azimuthand/or compass bearing of the image capture device. Informationconcerning the horizon angles of the image capture device and theinclination and declination of the image capture device may likewise becollected. Such metadata can be attached to both images and video.

The digital data organization process of the intelligent image sensor ofthe media capture device 1200 may be controlled manually, remotely, by auser or automatically by computer hardware/software control processes.These may include organization by photos, video, audio, location,position, by image capture device, by user, by date, time, logged user,subscription user, or a number of other attributes of animage/video/audio/media file. Likewise, these images may be madesearchable via these attributes in a network based (including “cloudbased”) storage system as well as a local storage system. In someembodiments, the captured image/video/media can also be stored andorganized by facial recognition means and subsequently searched or madesearchable by facial recognition applications.

FIG. 13 is a flow diagram illustrating an exemplary method for securitycertification and verification of digital media.

At step 1305, a media asset is captured by a sensor of a media capturedevice, optionally with its metadata as well. The metadata may include,for example, latitude and longitude coordinates from a GNSS receiver orother positioning receiver, an identification of the media capturedevice, a timestamp identifying date and time of capture, an altitude atcapture, a heading at capture, an inclination at capture, a yaw atcapture, a roll at capture, pitch at capture, a watermark, anannotation, any other data that might be found in image EXIF metadata,elevation or altitude, velocity at capture, path, speed, direction,distance, weather conditions, barometer reading & change, dew point,humidity, sun angle, temperature, compass heading, media certificationstatus, annotation certification status, incident note certificationsstatus, incident report certification status, event number, time, date,time zone, title, media type (IR, multi-spectrum, lidar, UV, 2dimensionality, 3D dimensionality), wind speed, wind direction, radardata, cloud coverage, visibility, flood data, any other metadatadiscussed herein, or combinations thereof.

At step 1310, an asymmetric public key infrastructure (PKI) keypair—with a private key and a corresponding public key—is generated bythe media capture device of step 1305 or by server 115. These may be RSA1024 asymmetric keys.

At step 1315, a digital signature is computed by generating a hashdigest—optionally using a secure hash algorithm such as SHA-0, SHA-1,SHA-2, or SHA-3—of the captured media, and optionally of the metadata aswell. At step 1320, the digital signature is encrypted with the privatekey. The media and/or metadata may also be encrypted using the privatekey. The private key is optionally destroyed at step 1325, or may simplynever be written to non-volatile memory in the first place.

At step 1330, the public key is published, either by sending it to theservers 115, to an authentication server such as a certificateauthority, or by otherwise sending it for publication in anotherpublicly accessible and trusted network location. At step 1335,verification as to the authenticity of the media and metadata may occurby decrypting the encrypted digital signature using the public keybefore or after publication at step 1330, and verifying whether or notthe hash digest stored as part of the decrypted digital signaturematches a newly generated hash digest of the media. If the new hashmatches the hash decrypted using the public key, then verification issuccessful, and the media asset has not been modified since capture (orat least since certification). If the new hash does not match the hashdecrypted using the public key, then verification is unsuccessful, andthe media asset has been modified since capture (or at least sincecertification). The same can be done using the metadata if a hash digestof the metadata is included in the digital signature. The verificationas to the authenticity of the media and metadata at step 1335 may alsoinclude decrypting the media asset and/or the metadata itself, if eitheror both were encrypted at step 1320. This verification may occur at thedigital media capture device—though it may instead or additionally beperformed at the server 115, for example before the server 115 indexesthe media as part of a cloud storage system accessible by client devices120.

Assuming the authentication of step 1335 was successful, a certifiedmedia dataset is generated by bundling the media, metadata, and theencrypted digital signature, for example in a zip file or othercompressed archive file. The public key may also be bundled with them,though additional security may be provided by publishing it elsewhere toa trusted authentication server. At step 1345, the certified mediadataset (and optionally the public key) is transmitted to a secondarydevice, such as a server 115 or a viewer device (i.e., a client device120).

In some cases, other data besides the media and associated metadata mayalso be certified, either or separately from the media asset asdiscussed further in the operations 1500 of FIG. 15 or together with thecertification of the media asset, in which case the hash and digitalsignatures at step 1315 may be hashes of the media asset as well as theother data, thereby certifying the media asset along with the otherdata.

In other words, the operations 1300 of FIG. 13 illustrate data integrityprecautions that can be taken. For example, all non-asset data can, insome embodiments, be secured in a local database with a globally uniqueidentifier to ensure its integrity. The asset's security and integritycan be ensured via a Digital Signature that is made up of a SHA1 digest,the time that the asset was captured and the device of origin. Thisallows the mobile app or server to detect changes due to storage ortransmission errors as well as any attempt to manipulate or change thecontent of the asset. The Digital Signature can be encrypted with apublic/private key-pair that is generated uniquely for that asset by themedia capture device. The private key can be destroyed by the mediacapture device and/or never written to a disk or stored in a memory ofthe media capture device or any other device; as such, this ensures thatthe asset cannot be re-signed and cannot be changed without thosechanges being detectable.

More specifically, media asset data, such as image, video, and/or audiodata, is captured by a camera, microphone, and/or other sensorsintegrated with the mobile device 105 and/or sensors connected to themobile device 105 in a wired or wireless manner. The mobile device 105also generates and/or extracts metadata (e.g., EXIF metadata)corresponding to this captured media asset, for example identifying themobile device 105 itself, a timestamp of capture, a date of capture, anauthor or owner of the mobile device 105, and any other metadata. Adigital signature is generated by generating a hash of both the capturedmedia and at least some of this metadata. For example, the digitalsignature may be a hash of the captured media, the timestamp, and anidentifier of the mobile device 105 that captured the media. The hashmay be computed using a secure hash algorithm (SHA), such as SHA-0,SHA-1, SHA-2, or SHA-3. The mobile device and/or cloud server generate apublic and private key pair using a public key infrastructure (PKI),where the keys may be for example RSA 1024 bit keys. The private key isused to encrypt the digital signature, and is then optionally deleted orerased/destroyed via overwriting for more security. The media asset, theencrypted digital signature, and the metadata are uploaded to the cloudsever system (optionally securely via HTTPS). The public key is alsouploaded (optionally securely via HTTPS), either to the same cloudserver system or to a different certificate authority (CA) server. Themedia asset and its metadata are now certified. Anyone can then retrievethe public key from the cloud server system or CA server and decrypt theencrypted digital signature to verify that it matches a hash taken ofthe media asset and metadata at a later time, thereby verifying that themedia asset and metadata have not been changed since certification. Insome cases, such a verification check is performed before the mediaasset and metadata and encrypted digital signature and public key aresent by the media capture device.

FIG. 14 is a flow diagram illustrating generation of a path of a capturedevice aligned to media captured by the capture device.

The operations 1400 of FIG. 14 may be performed, at least in part, byone or more processors of a media capture device, such as a video cameraor image camera or the mobile device 105. That is, the media capturedevice optionally includes one or more computing devices 1600 that eachinclude one or more processors. The process 1400 of FIG. 14 mayalternately or additionally be performed by one or more processors ofone or more computing devices 1600 that are coupled to the media capturedevice in a wired and/or wireless manner, such as the cloud serverstorage system 115.

At step 1405, the one or more processors receive, from a media capturedevice, a plurality of media assets captured by the media capture deviceduring a time period. The media assets may include one or more imagescaptured by a camera of the media capture device, one or more videoscaptured by a camera of the media capture device, one or more audiorecordings captured by a microphone of the media capture device, one ormore captures from a radio detection and ranging (RADAR) sensor of themedia capture device, one or more captures from a light detection andranging (LIDAR) sensor of the media capture device, one or more capturesfrom a sound navigation and ranging (SONAR) or sound detection andranging (SODAR) sensor of the media capture device, or some combinationthereof.

At step 1410, the one or more processors receive a plurality oftimestamps, each timestamp associated with capture of one of theplurality of media assets by the media capture device. Each of theplurality of timestamps falls within the time period. The timestamps maycorrespond to a moment in which a particular media asset was capturedwhen the capture occurs in an instant or during a short range of time,such as capture of an image by a camera or of media from a RADAR, LIDAR,SONAR, or SODAR sensor. The timestamps may correspond to a beginningand/or an end of capture of a particular media asset that is capturedover a duration of time—from a moment at which capture or recordingbegins to a moment at which capture or recording ends—such as a videocaptured by a camera or an audio recording captured by a microphone.Where the plurality of media assets include various types of media—suchas a mix of images and videos—the plurality of timestamps may includetimestamps of both types, which may include metadata tags identifyingwhat media asset the timestamp corresponds to and whether the timestampsignifies a moment of capture, a beginning of capture, or an end ofcapture.

At step 1415, the one or more processors receive a plurality oflocations, each location associated with capture of one of the pluralityof media assets by the media capture device. Each media asset may beassociated with one or more of the plurality of locations, and eachtimestamp may be associated with one or more of the plurality oflocations. That is, a location may be received that identifies alocation that the media capture device was in at a moment in which aparticular media asset was captured when the capture occurs in aninstant or during a short range of time, such as capture of an image bya camera or of media from a RADAR, LIDAR, SONAR, or SODAR sensor. Alocation may be received that identifies a location that the mediacapture device was in at a beginning and/or an end of capture of aparticular media asset that is captured over a duration of time—from amoment at which capture or recording begins to a moment at which captureor recording ends—such as a video captured by a camera or an audiorecording captured by a microphone. Where the plurality of media assetsinclude various types of media—such as a mix of images and videos—theplurality of locations may include locations of both types, which mayinclude metadata tags identifying what media asset the locationscorresponds to and whether the locations corresponds to a location ofthe media capture device at a moment of capture, a location of the mediacapture device at a beginning of capture, or a location of the mediacapture device at an end of capture. Each location may be identified bythe media capture device based on a positioning receiver of the mediacapture device, such as a GNSS receiver, a Bluetooth beacon positioningreceiver, a cell signal receiver, a WLAN receiver, or some combinationthereof.

At step 1420, the one or more processors generate a path of captures bythe media capture device during the time period, the path connecting theplurality of locations based on the plurality of timestamps. That is,each location of the plurality of locations is joined together by astraight or curved line in an order dictated by the timestamps that eachlocation corresponds to, or by an order of capture of the media assetsthat correspond to the locations, or some combination thereof. The pathsof FIG. 6, FIG. 8, FIG. 9, and FIG. 10 are examples of paths that may begenerated at step 1420.

In some cases, additional timestamps and corresponding locations may bereceived at steps 1410 and 1415 corresponding to one or more timesbetween capture of one media asset and capture of another media asset bythe media capture device. Additional timestamps and correspondinglocations may also be received at steps 1410 and 1415 corresponding toone or more times during capture of a media capture data set between thebeginning of capture and the end of capture, for example identifyingmultiple locations during capture of a video between the beginning ofrecording of the video and the end of recording of the video. Suchadditional locations may be used to generate a smoother path at step1420, or a path tracking the movement of the media assets periodicallyduring the entire time period, not just at moments related to an instantof capture, a beginning of capture, and/or an end of capture. Thisprevents missing data or large gaps in the path that is generated atstep 1420. For example, the path of FIG. 6 includes six locations thatcorrespond to image captures (and capture of additional data asdiscussed above), but the lines between the points corresponding to thesix captures are not straight—they instead curve along a path that themedia capture device followed between captures, which is identified atstep 1420 based on location and timestamp data captured between any twoof the captures.

The location data of step 1415 may include just latitude and longitudedata, or may alternately include other measurements, which may then beidentified and represented in the path. For example, the direction thatthe media capture device is facing (optionally including direction,heading, roll, pitch, and/or yaw) at a time corresponding to aparticular timestamp (e.g., at the beginning of capture, at the end ofcapture, during capture, or a different time) may be captured viasensors of the media capture device (e.g., one or more gyroscopes,accelerometers, altimeters, motion sensors, or combinations thereof),received by the one or more processors, and then represented in thepath, for example as in the arrows and field-of-view cones illustratedat each point of the top-down view path of FIG. 8. In some cases, thealtitude or elevation of the media capture device at a timecorresponding to a particular timestamp (e.g., at the beginning ofcapture, at the end of capture, during capture, or a different time) maybe captured via sensors of the media capture device (e.g., one or morealtimeters, gyroscopes, accelerometers, motion sensors, or combinationsthereof), received by the one or more processors, and then representedin the path, for example as in the vertical axis in the side-view paththat is illustrated at the bottom of FIG. 9 and within the report ofFIG. 10. The path generated at step 1420 may be a top-down view pathconnecting points that are charted along two directional latitude andlongitude axes, such as the path overlaid over the map of FIG. 6 or thepath of FIG. 8. The path generated at step 1420 may be a side view pathconnecting points that are charted along one directional axis and onealtitude axis, such as the path of path that is illustrated at thebottom of FIG. 9 and within the report of FIG. 10. In the side view pathof FIG. 9, the single directional axis may represent movement in aspecific direction (e.g., along a latitude axis or along a longitudeaxis or some axis in between) or may represent distance in any directionwithin the latitude-longitude plane.

At step 1425, the one or more processors render an interface for displayon a screen, the interface aligning the plurality of media assets alongthe path. The interface may overlay the path over a map as in FIG. 6,and may align images beside each capture location along the path.

FIG. 15 is a flow diagram illustrating tracking of media and its usethrough certification.

The operations 1500 of FIG. 15 may be performed, at least in part, byone or more processors of a media capture device, such as a video cameraor image camera or the mobile device 105. That is, the media capturedevice optionally includes one or more computing devices 1600 that eachinclude one or more processors. The process 1500 of FIG. 15 mayalternately or additionally be performed by one or more processors ofone or more computing devices 1600 that are coupled to the media capturedevice in a wired and/or wireless manner, such as the cloud serverstorage system 115 or the user/client computer 120.

At step 1505, the one or more processors receive a captured media assetand its associated metadata as captured by the media capture device. Atstep 1510, the one or more processors certify the media asset andoptionally its associated metadata as described with respect to theoperations 1300 of FIG. 13, thereby generating a certified media assetdataset as discussed with respect to step 1340 of FIG. 13. At step 1515,the one or more processors optionally verify that the certified mediaasset dataset is unchanged since its certification and then optionallysynchronize the certified media asset dataset with the cloud serversystem 115 by sending the certified media asset dataset to the cloudserver system 115, allowing the certified media asset dataset to beaccessed by user devices 120. Verification is performed by comparing anewly generated hash of the media asset to a hash extracted bydecrypting an encrypted digital signature from the certified media assetdataset using a public key associated with the certified media assetdataset as discussed further with respect to operations 1300 of FIG. 13.Optionally, step 1510 and/or step 1515 may be followed by step 1505 ifanother media asset is captured and certified; otherwise, step 1510and/or step 1515 may be followed by step 1520.

At step 1520, the one or more processors receive an annotationassociated with the media asset and/or of the certified media assetdataset, such as a voice note discussing the media asset or itsmetadata, a written note discussing the media asset or its metadata, ora graphical note (e.g., a marking on the media asset or its metadatathat circles or crosses out a portion of the media asset or itsmetadata). At step 1520, the one or more processors optionally alsoreceive metadata associated with the annotation, such as an author ofthe annotation, a category of the annotation, a title of the annotation,any other type of metadata discussed herein, or some combinationthereof. At step 1525, the one or more processors certify the annotationand optionally its associated metadata as described with respect to theoperations 1300 of FIG. 13, thereby generating a certified annotationdataset as discussed with respect to step 1340 of FIG. 13. That is, theoperations of FIG. 13 are performed, though the annotation is insertedin place of the media asset. Thus, the hash generated at step 1315 inthis situation is a hash of the annotation and/or of the metadata of theannotation, not a hash of the media asset or the metadata of the mediaasset. Alternately, the certified annotation dataset may be a certifiedversion of the media asset with the annotation included, for examplewhere the visual marking alters the media asset itself, and with themetadata of the annotation appended or included side-by-side with themetadata of the media asset. Thus, the hash generated at step 1315 inthis situation is a hash of the alerted media asset that includes theannotation and/or of the metadata of the annotation and the media asset.At step 1530, the one or more processors optionally verify that thecertified annotation dataset is unchanged since its certification andthen optionally synchronize the certified annotation dataset with thecloud server system 115 by sending the certified annotation dataset tothe cloud server system 115, allowing the certified annotation datasetto be accessed by user devices 120. Verification is performed bycomparing a newly generated hash of the annotation to a hash extractedby decrypting an encrypted digital signature from the certifiedannotation dataset using a public key associated with the certifiedannotation dataset as discussed further with respect to operations 1300of FIG. 13. Optionally, step 1525 and/or step 1530 may be followed bystep 1520 if another annotation is received and certified; otherwise,step 1525 and/or step 1530 may be followed by step 1535.

At step 1535, the one or more processors receive an incident descriptionof an incident associated with the media asset and/or of the certifiedmedia asset dataset and/or of the annotation and/or of the certifiedannotation dataset. The incident description describes the incidentusing a written note, a voice note, and/or an illustration input by auser or generated by a computing device. An incident description in thecontext of step 1535 (and the other steps of the operations 1500) mayalso include other analysis of the media asset, or of multiple mediaassets, that will be used for an incident report, such as the path 605generated in FIG. 6, the path 800 generated in FIG. 8, the map analysis910 of FIG. 9 and FIG. 10, the focuses analysis 920 of FIG. 9 and FIG.10, the elevation analysis 930 of FIG. 9 and FIG. 10, the incidentdescription 1020 of FIG. 10, the media mapping path 1010 of FIG. 10, orsome combination thereof. At step 1535, the one or more processorsoptionally also receive metadata associated with the incidentdescription, such as an author of the incident description, a categoryof the incident description, a title of the incident description, anyother type of metadata discussed herein, or some combination thereof. Atstep 1540, the one or more processors certify the incident descriptionand optionally its associated metadata as described with respect to theoperations 1300 of FIG. 13, thereby generating a certified incidentdescription dataset as discussed with respect to step 1340 of FIG. 13.That is, the operations of FIG. 13 are performed, though the incidentdescription is inserted in place of the media asset. Thus, the hashgenerated at step 1315 in this situation is a hash of the incidentdescription and/or of the metadata of the incident description, not ahash of the media asset or the metadata of the media asset. Alternately,the certified incident description dataset may be a certified version ofthe incident description alongside the certified media asset datasetand/or the certified annotation dataset, and with the metadata of theincident description appended or included side-by-side with the metadataof the media asset and/or the metadata of the annotation. Thus, the hashgenerated at step 1315 in this situation is a hash of the combination ofthe incident description, media asset, annotation, and/or metadata ofany combination of these three. At step 1545, the one or more processorsoptionally verify that the certified incident description dataset isunchanged since its certification and then optionally synchronize thecertified incident description dataset with the cloud server system 115by sending the certified incident description dataset to the cloudserver system 115, allowing the certified incident description datasetto be accessed by user devices 120. Verification is performed bycomparing a newly generated hash of the incident description to a hashextracted by decrypting an encrypted digital signature from thecertified incident description dataset using a public key associatedwith the certified incident description dataset as discussed furtherwith respect to operations 1300 of FIG. 13. Optionally, step 1540 and/orstep 1545 may be followed by step 1535 if another incident descriptionis received and certified; otherwise, step 1540 and/or step 1545 may befollowed by step 1550.

At step 1550, the one or more processors generate an incident reportthat includes the certified media asset dataset, the certifiedannotation dataset, and/or the certified incident description dataset.That is, the incident report may include any one or one, two, or threeof these. The incident report may also include the metadata for any one,two, or three of these, certified or not. One example of an incidentreport is illustrated in FIG. 10. At step 1550, the one or moreprocessors optionally also receive metadata associated with the incidentreport, such as an author of the incident report, a category of theincident report, a title of the incident report, any other type ofmetadata discussed herein, or some combination thereof. At step 1555,the one or more processors certify the incident report and optionallyits associated metadata as described with respect to the operations 1300of FIG. 13, thereby generating a certified report dataset as discussedwith respect to step 1340 of FIG. 13. That is, the operations of FIG. 13are performed, though the incident report is inserted in place of themedia asset. Thus, the hash generated at step 1315 in this situation isa hash of the incident report and/or of the metadata of the incidentreport, not a hash of the media asset or the metadata of the mediaasset. At step 1560, the one or more processors optionally verify thatthe certified report dataset is unchanged since its certification andthen optionally synchronize the certified report dataset with the cloudserver system 115 by sending the certified report dataset to the cloudserver system 115, allowing the certified report dataset to be accessedby user devices 120. Verification is performed by comparing a newlygenerated hash of the incident report to a hash extracted by decryptingan encrypted digital signature from the certified report dataset using apublic key associated with the certified report dataset as discussedfurther with respect to operations 1300 of FIG. 13.

The systems and methods described herein are more efficient, accurate,fraud resistant, consistent, portable, and convenient than any previousmethods or systems for adjusters. The unique mobile device and cloudserver system architecture also allows domains and secure user groupsfor multiple simultaneous users with complete data separation under usermanagement, user permission groups able to see data simultaneously ifthey hold the correct approved system user permissions and/orcredentials for their system domain or domains. That is, different usersmight be able to see different media assets and/or different incidentsdepending on permission levels and/or credentials associated withidentifiers (e.g., usernames, names, email addresses, badge numbers,employee numbers, etc.) of those individuals. Data is produced in a moreconsistent form using mobile application and cloud based process ofcollecting media and data in a collection system that is mobile andcloud based.

FIG. 16 is a block diagram of an exemplary computing device that may beused to implement some aspects of the subject technology. In particular,FIG. 16 illustrates an exemplary computing system 1600 that may be usedto implement some aspects of the subject technology. For example, any ofthe computing devices, computing systems, network devices, networksystems, servers, and/or arrangements of circuitry described herein mayinclude at least one computing system 1600, or may include at least onecomponent of the computer system 1600 identified in FIG. 16. Thecomputing system 1600 of FIG. 16 includes one or more processors 1610and memory 1620. Each of the processor(s) 1610 may refer to one or moreprocessors, controllers, microcontrollers, central processing units(CPUs), graphics processing units (GPUs), arithmetic logic units (ALUs),accelerated processing units (APUs), digital signal processors (DSPs),application specific integrated circuits (ASICs), field-programmablegate arrays (FPGAs), or combinations thereof. Each of the processor(s)1610 may include one or more cores, either integrated onto a single chipor spread across multiple chips connected or coupled together. Memory1620 stores, in part, instructions and data for execution by processor1610. Memory 1620 can store the executable code when in operation. Thesystem 1600 of FIG. 16 further includes a mass storage device 1630,portable storage medium drive(s) 1640, output devices 1650, user inputdevices 1660, a graphics display 1670, and peripheral devices 1680.

The components shown in FIG. 16 are depicted as being connected via asingle bus 1690. However, the components may be connected through one ormore data transport means. For example, processor unit 1610 and memory1620 may be connected via a local microprocessor bus, and the massstorage device 1630, peripheral device(s) 1680, portable storage device1640, and display system 1670 may be connected via one or moreinput/output (I/O) buses.

Mass storage device 1630, which may be implemented with a magnetic diskdrive or an optical disk drive, is a non-volatile storage device forstoring data and instructions for use by processor unit 1610. Massstorage device 1630 can store the system software for implementing someaspects of the subject technology for purposes of loading that softwareinto memory 1620.

Portable storage device 1640 operates in conjunction with a portablenon-volatile storage medium, such as a floppy disk, compact disk orDigital video disc, to input and output data and code to and from thecomputer system 1600 of FIG. 16. The system software for implementingaspects of the subject technology may be stored on such a portablemedium and input to the computer system 1600 via the portable storagedevice 1640.

The memory 1620, mass storage device 1630, or portable storage 1640 mayin some cases store sensitive information, such as transactioninformation, health information, or cryptographic keys, and may in somecases encrypt or decrypt such information with the aid of the processor1610. The memory 1620, mass storage device 1630, or portable storage1640 may in some cases store, at least in part, instructions, executablecode, or other data for execution or processing by the processor 1610.

Output devices 1650 may include, for example, communication circuitryfor outputting data through wired or wireless means, display circuitryfor displaying data via a display screen, audio circuitry for outputtingaudio via headphones or a speaker, printer circuitry for printing datavia a printer, or some combination thereof. The display screen may beany type of display discussed with respect to the display system 1670.The printer may be inkjet, laserjet, thermal, or some combinationthereof. In some cases, the output device circuitry 1650 may allow fortransmission of data over an audio jack/plug, a microphone jack/plug, auniversal serial bus (USB) port/plug, an Apple® Lightning® port/plug, anEthernet port/plug, a fiber optic port/plug, a proprietary wiredport/plug, a BLUETOOTH® wireless signal transfer, a BLUETOOTH® lowenergy (BLE) wireless signal transfer, a radio-frequency identification(RFID) wireless signal transfer, near-field communications (NFC)wireless signal transfer, 802.11 Wi-Fi wireless signal transfer,cellular data network wireless signal transfer, a radio wave signaltransfer, a microwave signal transfer, an infrared signal transfer, avisible light signal transfer, an ultraviolet signal transfer, awireless signal transfer along the electromagnetic spectrum, or somecombination thereof. Output devices 1650 may include any ports, plugs,antennae, wired or wireless transmitters, wired or wirelesstransceivers, or any other components necessary for or usable toimplement the communication types listed above, such as cellularSubscriber Identity Module (SIM) cards.

Input devices 1660 may include circuitry providing a portion of a userinterface. Input devices 1660 may include an alpha-numeric keypad, suchas a keyboard, for inputting alpha-numeric and other information, or apointing device, such as a mouse, a trackball, stylus, or cursordirection keys. Input devices 1660 may include touch-sensitive surfacesas well, either integrated with a display as in a touchscreen, orseparate from a display as in a trackpad. Touch-sensitive surfaces mayin some cases detect localized variable pressure or force detection. Insome cases, the input device circuitry may allow for receipt of dataover an audio jack, a microphone jack, a universal serial bus (USB)port/plug, an Apple® Lightning® port/plug, an Ethernet port/plug, afiber optic port/plug, a proprietary wired port/plug, a BLUETOOTH®wireless signal transfer, a BLUETOOTH® low energy (BLE) wireless signaltransfer, a radio-frequency identification (RFID) wireless signaltransfer, near-field communications (NFC) wireless signal transfer,802.11 Wi-Fi wireless signal transfer, cellular data network wirelesssignal transfer, a radio wave signal transfer, a microwave signaltransfer, an infrared signal transfer, a visible light signal transfer,an ultraviolet signal transfer, a wireless signal transfer along theelectromagnetic spectrum, or some combination thereof. Input devices1660 may include any ports, plugs, antennae, wired or wirelessreceivers, wired or wireless transceivers, or any other componentsnecessary for or usable to implement the communication types listedabove, such as cellular SIM cards.

Display system 1670 may include a liquid crystal display (LCD), a plasmadisplay, an organic light-emitting diode (OLED) display, an electronicink or “e-paper” display, a projector-based display, a holographicdisplay, or another suitable display device. Display system 1670receives textual and graphical information, and processes theinformation for output to the display device. The display system 1670may include multiple-touch touchscreen input capabilities, such ascapacitive touch detection, resistive touch detection, surface acousticwave touch detection, or infrared touch detection. Such touchscreeninput capabilities may or may not allow for variable pressure or forcedetection.

Peripherals 1680 may include any type of computer support device to addadditional functionality to the computer system. For example, peripheraldevice(s) 1680 may include a modem, a router, an antenna, a printer, abar code scanner, a quick-response (“QR”) code scanner, a document/imagescanner, a visible light camera, a thermal/infrared camera, anultraviolet-sensitive camera, a night vision camera, a light sensor, abattery, a power source, or some combination thereof.

The components contained in the computer system 1600 of FIG. 16 arethose typically found in computer systems that may be suitable for usewith some aspects of the subject technology and are intended torepresent a broad category of such computer components that are wellknown in the art. Thus, the computer system 1600 of FIG. 16 can be apersonal computer, a hand held computing device, a telephone (“smart” orotherwise), a mobile computing device, a workstation, a server (on aserver rack or otherwise), a minicomputer, a mainframe computer, atablet computing device, a wearable device (such as a watch, a ring, apair of glasses, or another type of jewelry/clothing/accessory), a videogame console (portable or otherwise), an e-book reader, a media playerdevice (portable or otherwise), a vehicle-based computer, somecombination thereof, or any other computing device. The computer system1600 may in some cases be a virtual computer system executed by anothercomputer system. The computer can also include different busconfigurations, networked platforms, multi-processor platforms, etc.Various operating systems can be used including Unix, Linux, Windows,Macintosh OS, Palm OS, Android, iOS, and other suitable operatingsystems.

In some cases, the computer system 1600 may be part of a multi-computersystem that uses multiple computer systems 1600, each for one or morespecific tasks or purposes. For example, the multi-computer system mayinclude multiple computer systems 1600 communicatively coupled togethervia at least one of a personal area network (PAN), a local area network(LAN), a wireless local area network (WLAN), a municipal area network(MAN), a wide area network (WAN), or some combination thereof. Themulti-computer system may further include multiple computer systems 1600from different networks communicatively coupled together via theinternet (also known as a “distributed” system).

Some aspects of the subject technology may be implemented in anapplication that may be operable using a variety of devices.Non-transitory computer-readable storage media refer to any medium ormedia that participate in providing instructions to a central processingunit (CPU) for execution and that may be used in the memory 1620, themass storage 1630, the portable storage 1640, or some combinationthereof. Such media can take many forms, including, but not limited to,non-volatile and volatile media such as optical or magnetic disks anddynamic memory, respectively. Some forms of non-transitorycomputer-readable media include, for example, a floppy disk, a flexibledisk, a hard disk, magnetic tape, a magnetic strip/stripe, any othermagnetic storage medium, flash memory, memristor memory, any othersolid-state memory, a compact disc read only memory (CD-ROM) opticaldisc, a rewritable compact disc (CD) optical disc, digital video disk(DVD) optical disc, a blu-ray disc (BDD) optical disc, a holographicoptical disk, another optical medium, a secure digital (SD) card, amicro secure digital (microSD) card, a Memory Stick® card, a smartcardchip, a Europay®/Mastercard®/Visa® (EMV) chip, a subscriber identitymodule (SIM) card, a mini/micro/nano/pico SIM card, another integratedcircuit (IC) chip/card, random access memory (RAM), static RAM (SRAM),dynamic RAM (DRAM), read-only memory (ROM), programmable read-onlymemory (PROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), flashEPROM (FLASHEPROM), cache memory (L1/L2/L3/L4/L5/L16), resistiverandom-access memory (RRAM/ReRAM), phase change memory (PCM), spintransfer torque RAM (STT-RAM), another memory chip or cartridge, or acombination thereof.

Various forms of transmission media may be involved in carrying one ormore sequences of one or more instructions to a processor 1610 forexecution. A bus 1690 carries the data to system RAM or another memory1620, from which a processor 1610 retrieves and executes theinstructions. The instructions received by system RAM or another memory1620 can optionally be stored on a fixed disk (mass storage device1630/portable storage 1640) either before or after execution byprocessor 1610. Various forms of storage may likewise be implemented aswell as the necessary network interfaces and network topologies toimplement the same.

While various flow diagrams provided and described above may show aparticular order of operations performed by some embodiments of thesubject technology, it should be understood that such order isexemplary. Alternative embodiments may perform the operations in adifferent order, combine certain operations, overlap certain operations,or some combination thereof.

The foregoing detailed description of the technology has been presentedfor purposes of illustration and description. It is not intended to beexhaustive or to limit the technology to the precise form disclosed.Many modifications and variations are possible in light of the aboveteaching. The described embodiments were chosen in order to best explainthe principles of the technology, its practical application, and toenable others skilled in the art to utilize the technology in variousembodiments and with various modifications as are suited to theparticular use contemplated. It is intended that the scope of thetechnology be defined by the claim.

What is claimed is:
 1. A method of media processing, the methodcomprising: receiving, from one or more sensors, a plurality of mediaassets captured by the one or more sensors during a time period;receiving a plurality of timestamps, each timestamp associated withcapture of one of the plurality of media assets by the one or moresensors, wherein each of the plurality of timestamps falls within thetime period; receiving a plurality of locations, each locationassociated with capture of one of the plurality of media assets by theone or more sensors; receiving a plurality of elevations, each elevationassociated with capture of one of the plurality of media assets by theone or more sensors; generating a path of captures of the plurality ofmedia assets, the path connecting the plurality of locations based onthe plurality of timestamps, wherein the path includes a graphicalrepresentation of a respective elevation for each location of theplurality of locations; and rendering an interface for display using adisplay, the interface graphically aligning the plurality of mediaassets and the plurality of elevations along the path.
 2. The method ofclaim 1, wherein each of the plurality of elevations is graphicallyrepresented in the path by a respective color from a plurality of colorsalong a color spectrum.
 3. The method of claim 1, wherein each of theplurality of elevations is graphically represented in the path by arespective shape from a plurality of shapes.
 4. The method of claim 1,wherein each of the plurality of elevations is graphically representedin the path by a respective position along an elevation axis.
 5. Themethod of claim 1, wherein each of the plurality of elevations isgraphically represented in the path by a respective number.
 6. Themethod of claim 1, further comprising: displaying the interface on thedisplay.
 7. The method of claim 1, wherein the one or more sensorsinclude an altimeter, wherein the plurality of elevations are receivedfrom the altimeter.
 8. The method of claim 1, wherein the one or moresensors include an image sensor, wherein the plurality of media assetsinclude one or more images captured by the image sensor.
 9. The methodof claim 1, further comprising: receiving a plurality of directions,each direction identifying where the one or more sensors was facingduring capture of one of the plurality of media assets, wherein the pathincludes a graphical representation of a respective direction of theplurality of directions for each location of the plurality of locations.10. The method of claim 1, further comprising: verifying that theplurality of media assets are unaltered since capture based on one ormore certification datasets.
 11. The method of claim 1, furthercomprising: identifying that a first subset of the path is in a firstgroup and that a second subset of the path is in a second group, whereinthe path includes a representation the first group and the second group.12. The method of claim 11, wherein the first group indicates an indoorarea and the second group indicates an outdoor area.
 13. A system formedia processing, the system comprising: one or more sensors thatcapture a plurality of media assets during a time period; a memorystoring instructions; and a processor that executes the instructions,wherein execution of the instructions by the processor causes theprocessor to: receive, from the one or more sensors, a plurality ofmedia assets captured by the one or more sensors during a time period;receive a plurality of timestamps, each timestamp associated withcapture of one of the plurality of media assets by the one or moresensors, wherein each of the plurality of timestamps falls within thetime period; receive a plurality of locations, each location associatedwith capture of one of the plurality of media assets by the one or moresensors; receive a plurality of elevations, each elevation associatedwith capture of one of the plurality of media assets by the one or moresensors; generate a path of captures of the plurality of media assets,the path connecting the plurality of locations based on the plurality oftimestamps, wherein the path includes a graphical representation of arespective elevation for each location of the plurality of locations;and render an interface for display using a display, the interfacegraphically aligning the plurality of media assets and the plurality ofelevations along the path.
 14. The system of claim 13, wherein each ofthe plurality of elevations is graphically represented in the path by atleast one of a respective color from a plurality of colors along a colorspectrum, a respective shape from a plurality of shapes, a respectiveposition along an elevation axis, or a respective number.
 15. The systemof claim 13, further comprising: a display that displays the interface.16. The system of claim 13, wherein the one or more sensors include analtimeter, wherein the plurality of elevations are received from thealtimeter.
 17. The system of claim 13, wherein the one or more sensorsinclude an image sensor, wherein the plurality of media assets includeone or more images captured by the image sensor.
 18. The system of claim13, further comprising: receiving a plurality of directions, eachdirection identifying where the one or more sensors was facing duringcapture of one of the plurality of media assets, wherein the pathincludes a graphical representation of a respective direction of theplurality of directions for each location of the plurality of locations.19. The system of claim 13, further comprising: verifying that theplurality of media assets are unaltered since capture based on one ormore certification datasets.
 20. The system of claim 13, furthercomprising: identifying that a first subset of the path is in a firstgroup and that a second subset of the path is in a second group, whereinthe path includes a representation the first group and the second group.